Meeting transcription using custom lexicons based on document history

ABSTRACT

A collaborative content management system allows multiple users to access and modify collaborative documents. When audio data is recorded by or uploaded to the system, the audio data may be transcribed or summarized to improve accessibility and user efficiency. Text transcriptions are associated with portions of the audio data representative of the text, and users can search the text transcription and access the portions of the audio data corresponding to search queries for playback. An outline can be automatically generated based on a text transcription of audio data and embedded as a modifiable object within a collaborative document. The system associates hot words with actions to modify the collaborative document upon identifying the hot words in the audio data. Collaborative content management systems can also generate custom lexicons for users based on documents associated with the user for use in transcribing audio data, ensuring that text transcription is more accurate.

TECHNICAL FIELD

The disclosed embodiments generally relate to the capture andtranscription of audio data, and more specifically to the accessibilityand use of audio data as a tool for effective meetings.

BACKGROUND

Online collaborative sharing of documents is typically provided by anetwork-based file sharing computer system that allows multiple users toaccess and edit the files. Generally, documents are created and editedby a specific type of native application, such as a word processor orspreadsheet application. Many such applications provide support forco-editing a single document among many users. Collaborative documentsmay be used for a variety of purposes, including for collaborationbetween multiple users in professional settings. There is a need forcollaborative systems to capture and manipulate audio data within or inconjunction with collaborative documents to make professionalcollaborations, such as meetings, more efficient for users.

SUMMARY

In some embodiments, a collaborative content management system accessesaudio data associated with a collaborative document. The audio data istranscribed into text, producing a text transcription. When the systemreceives a search query from a user accessing the collaborativedocument, the system identifies portions of the text transcriptioncorresponding to the query and receives a selection of one or moreresults (each corresponding to an identified portion of the texttranscription) from the user. Based on the selection of the searchresults, the system identifies portions of the audio data correspondingto the portion of the text transcription associated with the selectedresult and causes playback of the audio data portions. For instance, aplayback interface element can be displayed adjacent to a search resultthat, when selected, causes the playback of audio data corresponding tothe portion of the text transcription that corresponds to the searchresult.

In some embodiments, the collaborative content management systemaccesses audio data associated with a collaborative document. The audiodata is transcribed into text, producing a text transcription. Based onthe text transcription, the collaborative content management systemgenerates a text outline. The system then modifies the collaborativedocument associated with the audio data to incorporate the generatedtext outline, which can then be accessed and modified by users withaccess to the document.

In some embodiments, the collaborative content management systemidentifies hot words within the audio data associated with thecollaborative document, wherein each hot word is associated with anaction taken by the system to modify the document. As used herein, a“hot word” refers to a portion of text that denotes an action to betaken with regards to a document. For example, hot words may beassociated with actions to generate a summary, to modify objects withinthe document, or to modify the permissions associated with the document.The collaborative content management system modifies the collaborativedocument and displays the modified document. The modified document maythen be accessed, viewed, and modified by users with access permissionsto the document.

In some embodiments, the collaborative content management systemaccesses a custom lexicon based on documents associated with one or morespeakers in the audio data for use in generating the text transcriptionof the audio data. For example, a custom lexicon may be generated for auser based on vocabulary included within text documents, spreadsheets,slideshows, and other documents associated with the user on thecollaborative content management system. Using the custom lexicon, thecollaborative content management system transcribes the audio data intotext, and can modify the collaborative document associated with theaudio data to include the text transcript.

The features and advantages described in this summary and the followingdetailed description are not all-inclusive. Many additional features andadvantages will be apparent to one of ordinary skill in the art in viewof the drawings, specification, and claims hereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a system environment of a content managementsystem and a collaborative content management system according toexample embodiments.

FIG. 2 shows a block diagram of components of a client device, accordingto example embodiments.

FIG. 3 shows a block diagram of a content management system, accordingto example embodiments.

FIG. 4 shows a block diagram of a collaborative content managementsystem, according to example embodiments.

FIG. 5A shows an example user interface of a collaborative content itempage including various comments.

FIG. 5B shows an example user interface with a file-level commentassociated with the title of the collaborative content item.

FIG. 6A shows an example user interface with a plurality ofcollaborative content items, a list of notifications, and file levelcomments.

FIG. 6B shows an example of the data structures for collaborativecontent items, comments, and comment threads.

FIG. 7 shows an example illustrating a process for performing a keywordsearch of audio data.

FIG. 8 shows an example flow chart illustrating a method for audiocapture, search, and playback.

FIG. 9 shows an example illustrating the generation and incorporation ofa meeting summary into a document.

FIG. 10 shows an example flow chart illustrating a method for generatingand incorporating a meeting summary into a document.

FIG. 11 shows an example illustrating the generation and application ofa custom lexicon to create a meeting transcript.

FIG. 12 shows an example flow chart illustrating a method for generatinga text transcript using a custom lexicon based on document history.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following description that other alternativeembodiments of the structures and methods illustrated herein may beemployed without departing from the principles of the inventiondescribed herein.

DETAILED DESCRIPTION

System Overview

FIG. 1 shows a system environment including content management system100, collaborative content management system 130, and client devices120a, 120b, and 120c (collectively or individually “120”). Contentmanagement system 100 provides functionality for sharing content itemswith one or more client devices 120 and synchronizing content itemsbetween content management system 100 and one or more client devices120.

The content stored by content management system 100 can include any typeof content items, such as documents, spreadsheets, collaborative contentitems, text files, audio files, image files, video files, webpages,executable files, binary files, placeholder files that reference othercontent items, etc. In some implementations, a content item can be aportion of another content item, such as an image that is included in adocument. Content items can also include collections, such as folders,namespaces, playlists, albums, etc., that group other content itemstogether. The content stored by content management system 100 may beorganized in one configuration in folders, tables, or in other databasestructures (e.g., object oriented, key/value etc.).

In some embodiments, the content stored by content management system 100includes content items created by using third party applications, e.g.,word processors, video and image editors, database management systems,spreadsheet applications, code editors, and so forth, which areindependent of content management system 100.

In some embodiments, content stored by content management system 100includes content items, e.g., collaborative content items, created usinga collaborative interface provided by collaborative content managementsystem 130. In various implementations, collaborative content items canbe stored by collaborative content item management system 130, withcontent management system 100, or external to content management system100. A collaborative interface can provide an interactive content itemcollaborative platform whereby multiple users can simultaneously createand edit collaborative content items, comment in the collaborativecontent items, and manage tasks within the collaborative content items.

Users may create accounts at content management system 100 and storecontent thereon by sending such content from client device 120 tocontent management system 100. The content can be provided by users andassociated with user accounts that may have various privileges. Forexample, privileges can include permissions to: see content item titles,see other metadata for the content item (e.g. location data, accesshistory, version history, creation/modification dates, comments, filehierarchies, etc.), read content item contents, modify content itemmetadata, modify content of a content item, comment on a content item,read comments by others on a content item, or grant or remove contentitem permissions for other users.

Client devices 120 communicate with content management system 100 andcollaborative content management system 130 through network 110. Thenetwork may be any suitable communications network for datatransmission. In some embodiments, network 110 is the Internet and usesstandard communications technologies and/or protocols. Thus, network 110can include links using technologies such as Ethernet, 802.11, worldwideinteroperability for microwave access (WiMAX), 3G, 4G, digitalsubscriber line (DSL), asynchronous transfer mode (ATM), InfiniBand, PCIExpress Advanced Switching, etc. Similarly, the networking protocolsused on network 110 can include multiprotocol label switching (MPLS),the transmission control protocol/Internet protocol (TCP/IP), the UserDatagram Protocol (UDP), the hypertext transport protocol (HTTP), thesimple mail transfer protocol (SMTP), the file transfer protocol (FTP),etc. The data exchanged over network 110 can be represented usingtechnologies and/or formats including the hypertext markup language(HTML), the extensible markup language (XML), JavaScript Object Notation(JSON), etc. In addition, all or some of links can be encrypted usingconventional encryption technologies such as the secure sockets layer(SSL), transport layer security (TLS), virtual private networks (VPNs),Internet Protocol security (IPsec), etc. In other embodiments, theentities use custom and/or dedicated data communications technologiesinstead of, or in addition to, the ones described above.

In some embodiments, content management system 100 and collaborativecontent management system 130 are combined into a single system. Thesystem may include one or more servers configured to provide thefunctionality discussed herein for the systems 100 and 130.

Client Device

FIG. 2 shows a block diagram of the components of a client device 120according to one embodiment. Client devices 120 generally includedevices and modules for communicating with content management system 100and a user of client device 120. Client device 120 includes display 210for providing information to the user, and in certain client devices 120includes a touchscreen. Client device 120 also includes networkinterface 220 for communicating with content management system 100 vianetwork 110. There are additional components that may be included inclient device 120 but that are not shown, for example, one or morecomputer processors, local fixed memory (RAM and ROM), as well asoptionally removable memory (e.g., SD-card), power sources, andaudio-video outputs.

In certain embodiments, client device 120 includes additional componentssuch as camera 230 and location module 240. Location module 240determines the location of client device 120, using, for example, aglobal positioning satellite signal, cellular tower triangulation, orother methods. Location module 240 may be used by client application 200to obtain location data and add the location data to metadata about acontent item.

Client devices 120 maintain various types of components and modules foroperating the client device and accessing content management system 100.The software modules can include operating system 250 or a collaborativecontent item editor 270. Collaborative content item editor 270 isconfigured for creating, viewing and modifying collaborative contentitems such as text documents, code files, mixed media files (e.g., textand graphics), presentations or the like. Operating system 250 on eachdevice provides a local file management system and executes the varioussoftware modules such as content management system client application200 and collaborative content item editor 270. A contact directory 290stores information on the user's contacts, such as name, telephonenumbers, company, email addresses, physical address, website URLs, andthe like.

Client devices 120 access content management system 100 andcollaborative content management system 130 in a variety of ways. Clientdevice 120 may access these systems through a native application orsoftware module, such as content management system client application200. Client device 120 may also access content management system 100through web browser 260. As an alternative, the client application 200may integrate access to content management system 100 with the localfile management system provided by operating system 250. When access tocontent management system 100 is integrated in the local file managementsystem, a file organization scheme maintained at the content managementsystem is represented at the client device 120 as a local file structureby operating system 250 in conjunction with client application 200.

Client application 200 manages access to content management system 100and collaborative content management system 130. Client application 200includes user interface module 202 that generates an interface to thecontent accessed by client application 200 and is one means forperforming this function. The generated interface is provided to theuser by display 210. Client application 200 may store content accessedfrom a content storage at content management system 100 in local content204. While represented here as within client application 200, localcontent 204 may be stored with other data for client device 120 innon-volatile storage. When local content 204 is stored this way, thecontent is available to the user and other applications or modules, suchas collaborative content item editor 270, when client application 200 isnot in communication with content management system 100. Content accessmodule 206 manages updates to local content 204 and communicates withcontent management system 100 to synchronize content modified by clientdevice 120 with content maintained on content management system 100, andis one means for performing this function. Client application 200 maytake various forms, such as a stand-alone application, an applicationplug-in, or a browser extension.

Content Management System

FIG. 3 shows a block diagram of the content management system 100according to one embodiment. To facilitate the various contentmanagement services, a user can create an account with contentmanagement system 100. The account information can be maintained in useraccount database 316, and is one means for performing this function.User account database 316 can store profile information for registeredusers. In some cases, the only personal information in the user profileis a username and/or email address. However, content management system100 can also be configured to accept additional user information, suchas password recovery information, demographics information, paymentinformation, and other details. Each user is associated with a userIDand a user name. For purposes of convenience, references herein toinformation such as collaborative content items or other data being“associated” with a user are understood to mean an association between acollaborative content item and either of the above forms of useridentifier for the user. Similarly, data processing operations oncollaborative content items and users are understood to be operationsperformed on derivative identifiers such as collaborativeContentItemIDand userIDs. For example, a user may be associated with a collaborativecontent item by storing the information linking the userID and thecollaborativeContentItemID in a table, file, or other storage formats.For example, a database table organized by collaborativeContentItemIDscan include a column listing the userID of each user associated with thecollaborative content item. As another example, for each userID, a filecan list a set of collaborativeContentItemID associated with the user.As another example, a single file can list key values pairs such as<userID, collaborativeContentItemID> representing the associationbetween an individual user and a collaborative content item. The sametypes of mechanisms can be used to associate users with comments,threads, text elements, formatting attributes, and the like.

User account database 316 can also include account managementinformation, such as account type, e.g. free or paid; usage informationfor each user, e.g., file usage history; maximum storage spaceauthorized; storage space used; content storage locations; securitysettings; personal configuration settings; content sharing data; etc.Account management module 304 can be configured to update and/or obtainuser account details in user account database 316. Account managementmodule 304 can be configured to interact with any number of othermodules in content management system 100.

An account can be used to store content items, such as collaborativecontent items, audio files, video files, etc., from one or more clientdevices associated with the account. Content items can be shared withmultiple users and/or user accounts. In some implementations, sharing acontent item can include associating, using sharing module 310, thecontent item with two or more user accounts and providing for userpermissions so that a user that has authenticated into one of theassociated user accounts has a specified level of access to the contentitem. That is, the content items can be shared across multiple clientdevices of varying type, capabilities, operating systems, etc. Thecontent items can also be shared across varying types of user accounts.

Individual users can be assigned different access privileges to acontent item shared with them, as discussed above. In some cases, auser's permissions for a content item can be explicitly set for thatuser. A user's permissions can also be set based on: a type or categoryassociated with the user (e.g., elevated permissions for administratorusers or manager), the user's inclusion in a group or being identifiedas part of an organization (e.g., specified permissions for all membersof a particular team), and/or a mechanism or context of a user'saccesses to a content item (e.g., different permissions based on wherethe user is, what network the user is on, what type of program or APIthe user is accessing, whether the user clicked a link to the contentitem, etc.). Additionally, permissions can be set by default for users,user types/groups, or for various access mechanisms and contexts.

In some implementations, shared content items can be accessible to arecipient user without requiring authentication into a user account.This can include sharing module 310 providing access to a content itemthrough activation of a link associated with the content item orproviding access through a globally accessible shared folder.

The content can be stored in content storage 318, which is one means forperforming this function. Content storage 318 can be a storage device,multiple storage devices, or a server. Alternatively, content storage318 can be a cloud storage provider or network storage accessible viaone or more communications networks. In one configuration, contentmanagement system 100 stores the content items in the sameorganizational structure as they appear on the client device. However,content management system 100 can store the content items in its ownorder, arrangement, or hierarchy.

Content storage 318 can also store metadata describing content items,content item types, and the relationship of content items to variousaccounts, folders, or groups. The metadata for a content item can bestored as part of the content item or can be stored separately. In oneconfiguration, each content item stored in content storage 318 can beassigned a system-wide unique identifier.

Content storage 318 can decrease the amount of storage space required byidentifying duplicate files or duplicate segments of files. Instead ofstoring multiple copies of an identical content item, content storage318 can store a single copy and then use a pointer or other mechanism tolink the duplicates to the single copy. Similarly, content storage 318stores files using a file version control mechanism that tracks changesto files, different versions of files (such as a diverging versiontree), and a change history. The change history can include a set ofchanges that, when applied to the original file version, produces thechanged file version.

Content management system 100 automatically synchronizes content fromone or more client devices, using synchronization module 312, which isone means for performing this function. The synchronization is platformagnostic. That is, the content is synchronized across multiple clientdevices 120 of varying type, capabilities, operating systems, etc. Forexample, client application 200 synchronizes, via synchronization module312 at content management system 100, content in client device 120′sfile system with the content in an associated user account on system100. Client application 200 synchronizes any changes to content in adesignated folder and its sub-folders with the synchronization module312. Such changes include new, deleted, modified, copied, or moved filesor folders. Synchronization module 312 also provides any changes tocontent associated with client device 120 to client application 200.This synchronizes the local content at client device 120 with thecontent items at content management system 100.

Conflict management module 314 determines whether there are anydiscrepancies between versions of a content item located at differentclient devices 120. For example, when a content item is modified at oneclient device and a second client device, differing versions of thecontent item may exist at each client device. Synchronization module 312determines such versioning conflicts, for example by identifying themodification time of the content item modifications. Conflict managementmodule 314 resolves the conflict between versions by any suitable means,such as by merging the versions, or by notifying the client device ofthe later-submitted version.

A user can also view or manipulate content via a web interface generatedby user interface module 302. For example, the user can navigate in webbrowser 260 to a web address provided by content management system 100.Changes or updates to content in content storage 318 made through theweb interface, such as uploading a new version of a file, aresynchronized back to other client devices 120 associated with the user'saccount. Multiple client devices 120 may be associated with a singleaccount and files in the account are synchronized between each of themultiple client devices 120.

Content management system 100 includes communications interface 300 forinterfacing with various client devices 120, and with other contentand/or service providers via an Application Programming Interface (API),which is one means for performing this function. Certain softwareapplications access content storage 318 via an API on behalf of a user.For example, a software package, such as an app on a smartphone ortablet computing device, can programmatically make calls directly tocontent management system 100, when a user provides credentials, toread, write, create, delete, share, or otherwise manipulate content.Similarly, the API can allow users to access all or part of contentstorage 318 through a web site.

Content management system 100 can also include authenticator module 306,which verifies user credentials, security tokens, API calls, specificclient devices, etc., to determine whether access to requested contentitems is authorized, and is one means for performing this function.Authenticator module 306 can generate one-time use authentication tokensfor a user account. Authenticator module 306 assigns an expirationperiod or date to each authentication token. In addition to sending theauthentication tokens to requesting client devices, authenticator module306 can store generated authentication tokens in authentication tokendatabase 320. After receiving a request to validate an authenticationtoken, authenticator module 306 checks authentication token database 320for a matching authentication token assigned to the user. Once theauthenticator module 306 identifies a matching authentication token,authenticator module 306 determines if the matching authentication tokenis still valid. For example, authenticator module 306 verifies that theauthentication token has not expired or was not marked as used orinvalid. After validating an authentication token, authenticator module306 may invalidate the matching authentication token, such as asingle-use token. For example, authenticator module 306 can mark thematching authentication token as used or invalid, or delete the matchingauthentication token from authentication token database 320.

In some embodiments, content management system 100 includes a contentmanagement module 308 for maintaining a content directory thatidentifies the location of each content item in content storage 318, andallows client applications to request access to content items in thestorage 318, and which is one means for performing this function. Acontent entry in the content directory can also include a contentpointer that identifies the location of the content item in contentstorage 318. For example, the content entry can include a contentpointer designating the storage address of the content item in memory.In some embodiments, the content entry includes multiple contentpointers that point to multiple locations, each of which contains aportion of the content item.

In addition to a content path and content pointer, a content entry insome configurations also includes user account identifier thatidentifies the user account that has access to the content item. In someembodiments, multiple user account identifiers can be associated with asingle content entry indicating that the content item has shared accessby the multiple user accounts.

In some embodiments, the content management system 100 can include amail server module 322. The mail server module 322 can send (andreceive) collaborative content items to (and from) other client devicesusing the collaborative content management system 100. The mail servermodule can also be used to send and receive messages between users inthe content management system.

Collaborative Content Management System

FIG. 4 shows a block diagram of the collaborative content managementsystem 130, according to one embodiment. Collaborative content items canbe files that users can create and edit using a collaborative contentitems editor 270 and can contain collaborative content item elements.Collaborative content item elements may include any type of content suchas text; images, animations, videos, audio, or other multi-media;tables; lists; references to external content; programming code; tasks;tags or labels; comments; or any other type of content. Collaborativecontent item elements can be associated with an author identifier,attributes, interaction information, comments, sharing users, etc.Collaborative content item elements can be stored as database entities,which allows for searching and retrieving the collaborative contentitems. As with other types of content items, collaborative content itemsmay be shared and synchronized with multiple users and client devices120, using sharing 310 and synchronization 312 modules of contentmanagement system 100. Users operate client devices 120 to create andedit collaborative content items, and to share collaborative contentitems with other users of client devices 120. Changes to a collaborativecontent item by one client device 120 are propagated to other clientdevices 120 of users associated with that collaborative content item.

In the embodiment of FIG. 1, collaborative content management system 130is shown as separate from content management system 100 and cancommunicate with it to obtain its services. In other embodiments,collaborative content management system 130 is a subsystem of thecomponent of content management system 100 that provides sharing andcollaborative services for various types of content items. User accountdatabase 316 and authentication token database 320 from contentmanagement system 100 are used for accessing collaborative contentmanagement system 130 described herein.

Collaborative content management system 130 can include various serversfor managing access and edits to collaborative content items and formanaging notifications about certain changes made to collaborativecontent items. Collaborative content management system 130 can includeproxy server 402, collaborative content item editor 404, backend server406, and collaborative content item database 408, access link module410, copy generator 412, collaborative content item differentiator 414,settings module 416, metadata module 418, revision module 420,notification server 422, and notification database 424. Proxy server 402handles requests from client applications 200 and passes those requeststo the collaborative content item editor 404. Collaborative content itemeditor 404 manages application level requests for client applications200 for editing and creating collaborative content items, andselectively interacts with backend servers 406 for processing lowerlevel processing tasks on collaborative content items, and interfacingwith collaborative content items database 408 as needed. Collaborativecontent items database 408 contains a plurality of database objectsrepresenting collaborative content items, comment threads, and comments.Each of the database objects can be associated with a content pointerindicating the location of each object within the CCI database 408 .Notification server 422 detects actions performed on collaborativecontent items that trigger notifications, creates notifications innotification database 424, and sends notifications to client devices.

Client application 200 sends a request relating to a collaborativecontent item to proxy server 402. Generally, a request indicates theuserID (“UID”) of the user, and the collaborativeContentItemID (“NID”)of the collaborative content item, and additional contextual informationas appropriate, such as the text of the collaborative content item. Whenproxy server 402 receives the request, the proxy server 402 passes therequest to the collaborative content item editor 404. Proxy server 402also returns a reference to the identified collaborative content itemsproxy server 402 to client application 200, so the client applicationcan directly communicate with the collaborative content item editor 404for future requests. In an alternative embodiment, client application200 initially communicates directly with a specific collaborativecontent item editor 404 assigned to the userID.

When collaborative content item editor 404 receives a request, itdetermines whether the request can be executed directly or by a backendserver 406. When the request adds, edits, or otherwise modifies acollaborative content item the request is handled by the collaborativecontent item editor 404. If the request is directed to a database orindex inquiry, the request is executed by a backend server 406. Forexample, a request from client device 120 to view a collaborativecontent item or obtain a list of collaborative content items responsiveto a search term is processed by backend server 406.

The access module 410 receives a request to provide a collaborativecontent item to a client device. In some embodiments, the access modulegenerates an access link to the collaborative content item, for instancein response to a request to share the collaborative content item by anauthor. The access link can be a hyperlink including or associated withthe identification information of the CCI (i.e., unique identifier,content pointer, etc.). The hyperlink can also include any type ofrelevant metadata within the content management system (i.e., author,recipient, time created, etc.). In some embodiments, the access modulecan also provide the access link to user accounts via the network 110,while in other embodiments the access link can be provided or madeaccessible to a user account and is accessed through a user account viathe client device. In some embodiments, the access link will be ahyperlink to a landing page (e.g., a webpage, a digital store front, anapplication login, etc.) and activating the hyperlink opens the landingpage on a client device. The landing page can allow client devices notassociated with a user account to create a user account and access thecollaborative content item using the identification informationassociated with the access link. Additionally, the access link modulecan insert metadata into the collaborative content item, associatemetadata with the collaborative content item, or access metadataassociated with the collaborative content item that is requested.

The access module 410 can also provide collaborative content items viaother methods. For example, the access module 410 can directly send acollaborative content item to a client device or user account, store acollaborative content item in a database accessible to the clientdevice, interact with any module of the collaborative content managementsystem to provide modified versions of collaborative content items(e.g., the copy generator 412, the CCI differentiator 414, etc.),sending content pointer associated with the collaborative content item,sending metadata associated with the collaborative content item, or anyother method of providing collaborative content items between devices inthe network. The access module can also provide collaborative contentitems via a search of the collaborative content item database (i.e.,search by a keyword associated with the collaborative content item, thetitle, or a metadata tag, etc.).

The copy generator 412 can duplicate a collaborative content item.Generally, the copy generator duplicates a collaborative content itemwhen a client device selects an access link associated with thecollaborative content item. The copy generator 412 accesses thecollaborative content item associated with the access link and creates aderivative copy of the collaborative content item for every requestreceived. The copy generator 412 stores each derivative copy of thecollaborative content item in the collaborative content item database408. Generally, each copy of the collaborative content item that isgenerated by the copy generator 412 is associated with both the clientdevice from which the request was received and the user accountassociated with the client device requesting the copy. When the copy ofthe collaborative content item is generated it can create a new uniqueidentifier and content pointer for the copy of the collaborative contentitem. Additionally, the copy generator 412 can insert metadata into thecollaborative content item, associate metadata with the copiedcollaborative content item, or access metadata associated with thecollaborative content item that was requested to be copied.

The collaborative content item differentiator 414 determines thedifference between two collaborative content items. In some embodiments,the collaborative content item differentiator 414 determines thedifference between two collaborative content items when a client deviceselects an access hyperlink and accesses a collaborative content itemthat the client device has previously used the copy generator 412 tocreate a derivative copy. The content item differentiator can indicatethe differences between the content elements of the comparedcollaborative content items. The collaborative content itemdifferentiator 414 can create a collaborative content item that includesthe differences between the two collaborative content items, i.e. adifferential collaborative content item. In some embodiments, thecollaborative content item differentiator provides the differentialcollaborative content item to a requesting client device 120. Thedifferentiator 414 can store the differential collaborative content itemin the collaborative content item database 408 and generateidentification information for the differential collaborative contentitem. Additionally, the differentiator 414 can insert metadata into theaccessed and created collaborative content items, associate metadatawith the accessed and created collaborative content item, or accessmetadata associated with the collaborative content items that wererequested to be differentiated.

The settings and security module 416 can manage security duringinteractions between client devices 120, the content management system100, and the collaborative content management system 130. Additionally,the settings and security module 416 can manage security duringinteractions between modules of the collaborative content managementsystem. For example, when a client device 120 attempts to interactwithin any module of the collaborative content management system 100,the settings and security module 416 can manage the interaction bylimiting or disallowing the interaction. Similarly, the settings andsecurity module 416 can limit or disallow interactions between modulesof the collaborative content management system 130. Generally, thesettings and security module 416 accesses metadata associated with themodules, systems 100 and 130, devices 120, user accounts, andcollaborative content items to determine the security actions to take.Security actions can include: requiring authentication of client devices120 and user accounts, requiring passwords for content items, removingmetadata from collaborative content items, preventing collaborativecontent items from being edited, revised, saved or copied, or any othersecurity similar security action. Additionally, settings and securitymodule can access, add, edit or delete any type of metadata associatedwith any element of content management system 100, collaborative contentmanagement system 130, client devices 120, or collaborative contentitems.

The metadata module 418 manages metadata within with the collaborativecontent management system. Generally, metadata can take three formswithin the collaborative content management system: internal metadata,external metadata, and device metadata. Internal metadata is metadatawithin a collaborative content item, external metadata is metadataassociated with a CCI but not included or stored within the CCI itself,and device metadata is associated with client devices. At any point themetadata module can manage metadata by changing, adding, or removingmetadata.

Some examples of internal metadata can be: identifying informationwithin collaborative content items (e.g., email addresses, names,addresses, phone numbers, social security numbers, account or creditcard numbers, etc.); metadata associated with content elements (e.g.,location, time created, content element type; content element size;content element duration, etc.); comments associated with contentelements (e.g., a comment giving the definition of a word in acollaborative content item and its attribution to the user account thatmade the comment); or any other metadata that can be contained within acollaborative content item.

Some examples of external metadata can be: content tags indicatingcategories for the metadata; user accounts associated with a CCI (e.g.,author user account, editing user account, accessing user account etc.);historical information (e.g., previous versions, access times, edittimes, author times, etc.); security settings; identifying information(e.g., unique identifier, content pointer); collaborative contentmanagement system 130 settings; user account settings; or any othermetadata that can be associated with the collaborative content item.

Some examples of device metadata can be: device type; deviceconnectivity; device size; device functionality; device sound anddisplay settings; device location; user accounts associated with thedevice; device security settings; or any other type of metadata that canbe associated with a client device 120.

The collaborative content item revision module 420 manages applicationlevel requests for client applications 200 for revising differntialcollaborative content items and selectively interacts with backendservers 406 for processing lower level processing tasks on collaborativecontent items, and interfacing with collaborative content items database408 as needed. The revision module can create a revised collaborativecontent item that is some combination of the content elements from thedifferential collaborative content item. The revision module 420 canstore the revised collaborative content item in the collaborativecontent item database or provide the revised collaborative content itemto a client device 120. Additionally, the revision module 420 can insertmetadata into the accessed and created collaborative content items,associate metadata with the accessed and created collaborative contentitem, or access metadata associated with the collaborative content itemsthat were requested to be differentiated.

Content management system 100 and collaborative content managementsystem 130 may be implemented using a single computer, or a network ofcomputers, including cloud-based computer implementations. Theoperations of content management system 100 and collaborative contentmanagement system 130 as described herein can be controlled througheither hardware or through computer programs installed in computerstorage and executed by the processors of such server to perform thefunctions described herein. These systems include other hardwareelements necessary for the operations described here, including networkinterfaces and protocols, input devices for data entry, and outputdevices for display, printing, or other presentations of data, but whichare not described herein. Similarly, conventional elements, such asfirewalls, load balancers, collaborative content items servers, failoverservers, network management tools and so forth are not shown so as notto obscure the features of the system. Finally, the functions andoperations of content management system 100 and collaborative contentmanagement system 130 are sufficiently complex as to requireimplementation on a computer system, and cannot be performed in thehuman mind simply by mental steps.

Comment Management User Interface

Referring now to FIG. 5A, there is shown an example user interface witha page of a collaborative content item 502 entitled “Draft Speech” inwhich several comments 504 associated with the collaborative contentitem have been made. In this example, a collaborative content item 502is composed of content such as lines of text, which can be arranged suchas in paragraph blocks 508, and may include any other form of media,such as images, videos, spreadsheets, executable or interpretable code,and so forth.

Content Level Comments

A collaborative content item 502 can have zero or more content levelcomments 504. Content level comments can be associated with specificportions of a collaborative content item. The presence of content levelcomments 504 within the content item may be indicated by underlined (orcolored underlined) portions 510 of content, though any other formattingmay be used to indicate the presence of a content level comment 504(e.g., lines connecting the content level comments to the content item,comment numbers in superscript form, highlighting, a “hover over”display indicator etc.). The portion 510 of content with which a contentlevel comment is associated is also called a span. Content levelcomments 504 can be associated with overlapping spans; the first andsecond content level comments 504a, 504b are applied to the span “Now weare engaged in a great civil war, testing whether that nation, or anynation so conceived, and so dedicated, can long endure” and the thirdcomment 504c is associated with just the span “This we may, in allpropriety do.”

The content level comments 504 can be arranged in a comment pane 512positioned to the side of the body of the collaborative content item502. Each content level comment 504 has an author 514 (indicated by username) and a creation date and time. A collection of comments thattogether form an exchange between users with respect to a single span isa thread 518. Threads are displayed proximate the span that isassociated with the thread. In the example of FIG. 5A, there are threethreads, 518 a, 518 b, and 518 c; thread 518 a has a total of fourcomments (two shown, and “2 more comments” as indicated) and the otherthreads have one comment each.

A user may create a new comment or reply to existing comment. To createa comment, a user selects a span in the content item, and activates acomment function, for example via button 522, menu or other input. Thenew comment 504 is displayed in the comment pane 512, indicating theuser name and creation time, and the user may then enter text for thecomment therein. The user can apply text formatting to the text of thecomment as done for formatting the text of the collaborative contentitem. A user may also create a comment to include in a thread byentering text into a reply field 516 in one of the comments 504, such asthe most recent comment in a thread 518.

When a user opens a collaborative content item initially, the commentpane 512 can be closed such that the comments therein are hidden. Theuser can activate the comment pane 512 to show the content levelcomments by selecting text (e.g., double clicking) text that isformatted or otherwise indicated as having an associated comment. Insome implementations, the comment pane 512 can be visible when acollaborative content item is opened. The pane 512 includes a counter524 of the current number of content level comments in the collaborativecontent item that are visible to the user. Each comment can have astate, as to whether the comment is active or resolved. The counter 524serves as a menu that the user can select from to filter the comments soas to show all comments, active comments or resolved comments.

A collaborative content item may also include a share icon 526 thatallows a user to share the collaborative content item with other usersof the content management system 100. Upon clicking on the share icon526 a sharing interface is displayed to the user. The sharing interfacecan include a field for adding user names or email addresses to the listof users with which the collaborative content item is to be shared. Thesharing interface may also include a text field to allow the sharinguser to send a message to users receiving the request to share thecollaborative content item.

User Primitives

In some embodiments, the collaborative content management system 130 isconfigured to recognize particular text patterns as functionalprimitives that activate various functions of the collaborative contentmanagement system 130. One type of functional primitive is a userprimitive. A user primitive is indicated by a predetermined tokenfollowed by the user name of a user. The user primitive is used in thetext or comments of a collaborative content item to programmaticallyassociate a specific user with the collaborative content item orcomment. Colloquially, the appearance of a user primitive identifying auser name is called a mention of a user.

In some embodiments, the user primitive takes the form of @usernamewhere the “@” symbols is a predetermined token indicates to thecollaborative content management system 130 that the following stringusername is the user name of a system user. Referring to FIG. 5A,several examples of user primitives 520 are illustrated. First in thetext of the collaborative content item, the first sentence includes theuser primitives “@Bill_Seward” and “@John_Hay. The user primitive“@Bill_Seward” is also shown in the text of comment 504 d. Thecollaborative content management system 130 recognizes these primitivesas it processes the text of the collaborative content item and comments.

When a user primitive indicating a specific user appears in the span fora thread, or the text of a comment, the collaborative content managementsystem 130 includes the userID for the indicated user in the audiencefor thread containing the comment. This allows the mentioned user to seethe entire thread in which they are mentioned when accessing thecollaborative content item (since access to the thread when opening acollaborative content item is determined by presence of a user's ID inthe audience), as well for a mechanism to notify the user, as nextdescribed.

In some embodiments, when a user primitive occurs elsewhere in thecollaborative content item, but outside of the span for the thread, theuserID for the mentioned user is included in the audience. For example,if a user is mentioned in the same paragraph as the span for a thread,the userID for the user is included in the audience.

Contextual Primitives

In addition to user primitives, the collaborative content managementsystem 130 may also support contextual primitives. Contextual primitivesfunction in a similar way to user primitives, however, instead of addinga single user to the audience of a thread, contextual primitives can adda group of users, or user(s) assigned to a specific role (e.g., owner,editor, etc.), to the audience of a thread using document context. Acontextual primitive is indicated by a predetermined token followed by apredetermined text string. Each predefined text string may incurdifferent functionality from the collaborative content management system130. A user inserts the contextual primitive as they are editing thecontent item.

In some implementations, including the @doc primitive can cause everyuser with access to the collaborative content item to be included in theaudience of a thread that includes the primitive. An algorithm toachieve this functionality is as follows. The collaborative contentmanagement system 130 detects the “@doc” text string in the span of athread or in a comment content and accesses the collaborative contentitem index of the collaborative content item database 408. Thecollaborative content management system 130 determines the userIDs withviewing privileges for the collaborative content item according to thecollaborative content item index and adds those userIDs to theaudience_list for the thread. Alternatively, as discussed below, thesystem can include an entry in the collaborative content item audiencelist indicating that multiple users such as all users, authenticatedusers, users that are part of a particular group, etc., should beincluded as audience members. When the collaborative content item issubsequently accessed, the thread including the “@doc” primitive will bevisible to all users viewing the collaborative content item.Additionally, any notification generating activity in the thread will bereported to all users in the collaborative content item.

In some embodiments, the “@doc” primitive is dynamic such that any usersthat are added to the collaborative content item even after the threadhas been created will be able to view the comment thread. This may beaccomplished by reevaluating the span of a thread and the comment textof a thread each time the collaborative content item is compiled.Alternatively, instead of adding userIDs to the audience_list of athread directly, the collaborative content management system 130 maycreate a special ID value indicating that the “@doc” primitive has beenused. Therefore, during compilation of the collaborative content item,the collaborative content management system 130 checks to see if aparticular thread should be displayed to a viewing user by referencingthe audience_list of the thread. If the collaborative content managementsystem 130 detects the special ID associated with the “@doc” primitiveit will reference the collaborative content item database 408 todetermine which users have viewing permissions. If the user ID of thecurrent user is included in the collaborative content item database 408then the collaborative content management system 130 displays the threadto the current user.

In addition the collaborative content item audience primitive, othercontextual primitives may be implemented:

The “@folder” primitive informs the collaborative content managementsystem 130 that all users with access to the folder that includes thecollaborative content item should be able to view the thread. In thiscase, some of the users that have access to the folder may not haveaccess to the collaborative content item. In this case, thecollaborative content management system 130 may grant all users withaccess to the folder access to the collaborative content item, provide aseparate interface for users without access to the collaborative contentitem to view the thread, or it may provide the users without access tothe collaborative content item with notifications regarding the threadover email.

The “@editing” primitive indicates that all users with editing access tothe collaborative content item are to be included in the audience for athread. The collaborative content management system 130 parses this inthe same way as the “@doc” primitive. However, instead of retrieving allusers associated with the collaborative content item in thecollaborative content item index only users with editing access areadded to the audience_list for the thread. The “@sharing” primitive(only users with sharing privileges are added to the audience_list)functionality is implemented in a similar manner.

The “@threads” primitive adds all users that have participated inthreads in the collaborative content item already to the audience_listof the current thread. To accomplish this, upon detecting the “@threads”primitive the collaborative content management system 130 accesses eachthread object associated with the collaborativeContentItemID and addsany users listed in the audience list of those threads the audience listof the current thread.

Depending on the embodiment, the specific text string associated withthe primitive may be different. A user may also define their owncontextual primitive using the client application to select users,categories of users, and contextual categories of users to be includedin the primitive. Additionally, and contextual primitive may be madedynamic using a special ID in the audience_list which triggers areevaluation of the audience list during compilation of thecollaborative content item.

File-level Comment Interfaces

The collaborative content management system 130 also enables file-levelcommenting and may utilize a number of user interfaces depending on theembodiment. A file-level comment is associated with the file itself andpersists with the file until the file is deleted or the comment itselfis deleted. This allows for conversations between users to occur on afile-level that persists with each iteration on the file. The methodsdescribed herein, also allow for the simultaneous display of thecollaborative content item and file-level comments so a user can reviewthe collaborative content item and make comments on the collaborativecontent item without having to change windows. File-level comments havemany of the same characteristics as the content level comments and relyon the same underlying data structure. However, file-level comments arenot associated with a span of the collaborative content item and areinstead associated with the entirely of the content item. Despite thesedifferences, file-level comments may be used to form threads and have anassociated author, creation time and date, which may be displayed in asimilar fashion as in content level comments depending on theembodiment.

Because file-level comments are not associated with a particular span ofthe collaborative content item, different UI elements may be used todisplay the file-level comments. FIG. 5B illustrates an embodiment forcreating and displaying file-level comments.

FIG. 5B shows an example user interface with a file-level commentassociated with the title of the collaborative content item. FIG. 5Bdisplays the same six comments and four threads as in FIG. 5A, with theaddition of a file-level comment 528. The file-level comment isdisplayed alongside the content level comments in the comment pane 512.Instead of being for a particular span in the collaborative contentitem, as with the content level comments, the file-level comment 528 isassociated with the entire document, and is indicated in thecollaborative content item by visually distinguishing features 531, suchas formatting or highlighting, borders or the like to the title of thecollaborative content item 530. Optionally, the same visuallydistinguishing features can be applied to the comment itself, so thatthe user knows that which comments are associated with the file andwhich with specific spans of the content item. FIG. 5B also illustratesthe use of a file-level primitive 532, “@file”, to indicate that acomment is file-level comment rather than a content level comment.

User Interface for Displaying a List of Notifications

FIG. 6 shows an example user interface with a list of collaborativecontent items 602 and a list of notifications 604. This user interfaceallows a viewing user to view the collaborative content items to whichthe viewing user has been granted access (hereinafter “the user'scollaborative content items”). As referred to herein, the “viewing user”is the user viewing the user interfaces described herein. In thisexample, the collaborative content management system 130 has granted theviewing user access to multiple collaborative content items, includingthe five collaborative content items 606A through 606F shown in the“recent docs” tab 608 of the user interface. The user interface alsoincludes “created by me” and “shared with me” tabs 610, 612 that theviewing user can select to access additional lists of collaborativecontent items.

When other users make certain types of changes to the viewing user'scollaborative content items, the collaborative content management system130 generates a notification of the change. The collaborative contentmanagement system 130 defines one or more triggering actions. Atriggering action is a change made by another user that causes thecollaborative content management system 130 to create a notificationabout the change and provide the notification to the client device ofthe viewing user. For example, a triggering action may occur whenanother user adds or alters a portion of the collaborative content item,or adds a comment to a thread, for example in a thread that alreadyincludes a comment added by the viewing user.

The client application 200 receives notifications from the collaborativecontent management system 130 and can display a notification in avariety of ways. One way of displaying a notification is thenotification list 604 shown in FIG. 6. The notification list 604includes notifications for several of the viewing user's collaborativecontent items, and it is displayed when the viewing user selects thenotification icon 614. In the example shown in FIG. 6, the notificationsin the notification list 604 are sorted by the age of collaborativecontent item, and the notifications for each collaborative content itemare sorted from most recent to least recent.

The client application 200 displays each notification in thenotification list 604 with notification text and a short phraseindicating whether the notification relates to a comment or a portion oftext in the collaborative content item content. Although not explicitlyshown in FIG. 6, each notification can also include a content span and anotification link. The content span associates the notification with aspan of content in a collaborative content item 502. The notificationlink is a link to the collaborative content item and includes a pointerto the content span. A user input selecting a notification in thenotification list 604 selects the link. The selection of the link causesthe client application 200 to open the collaborative content item to aposition where the content span is visible. As a beneficial result andimprovement in functionality, the user does not have to scroll throughthe collaborative content item to find the change that was the subjectof the notification.

Referring to the final notification 616 in the notification list 604 asan example, the notification text is the user primitive “@Bill Seward”and the adjacent text “your thoughts.” A user primitive is indicated bya predetermined token followed by the user name of a user. The userprimitive is used in the text or comments of a collaborative contentitem to programmatically associate a specific user with thecollaborative content item or comment. Colloquially, the appearance of auser primitive identifying a user name is called a mention of a user. Insome embodiments, the user primitive takes the form of @username wherethe “@” symbol is a predetermined token that indicates to thecollaborative content management system 130 that the following string“username” is the user name of a system user. In some implementations,other predetermined tokens can be used to indicate a primitive. If theuser selects this notification 616, the notification link causes theclient application 200 to open the collaborative content item 502 shownin FIG. 5A to a position where the span 510 b is visible.

If the notification is generated in response to a file-level comment,the file-level comment may have no associated span in the associatedcollaborative content item or may set the span to be the collaborativecontent item title. The link included in the notification may open thecollaborative content item displaying the beginning of the content orthe title. [0090] In addition to displaying notifications for file-levelcomments in notification list 604, the client application 200 may alsodisplay a file-level thread pane 618, which displays file-level commentthreads corresponding to a selected collaborative content item 620. Insome implementations, file-level thread pane 618 can display file-levelcomment threads corresponding to multiple selected collaborative contentitems. In some implementations, file level thread pane 618 can displayfile-level comment threads corresponding to multiple of collaborativecontent items 606, whether or not the collaborative content items areselected. In the illustrated example, file-level comments from thecollaborative content item titled “Draft Speech” are displayed in thefile-level thread pane 618. In some embodiments, users may utilize thefile-level thread pane 618 to add or reply to file-level commentswithout opening the associated collaborative content item. [0091] Invarious implementations, any of collaborative content items, theassociated comments, or collaborative content item file structure andother metadata can be locally stored on a client device. For example,content can be downloaded from the collaborative content managementsystem 130 for use in an offline mode. The inclusion of a file-levelthread pane 618 may be especially beneficial for this offline use wherefile-level comments may be downloaded for offline viewing in thefile-level thread pane 618. This would allow users to receive someinformation about collaborative content items without having to storethe enter contents of the collaborative content items locally. Forexample, users may view file-level comments for collaborative contentitems listed in file-level thread pane 618, without requiring thecollaborative content items to also be locally stored.

Database Structures

Referring to FIG. 6B, collaborative content item database 408 (CCIdatabase) stores the collaborative content items, content level andfile-level comments, and threads as database entities, and providesprogrammatic access thereto for searching and retrieving these entitiesand is one means for performing these functions. The CCI database 408can be implemented in a relational form using separate tables forcollaborative content items, threads, and comments, or using objects,BLOBs, files, or other structures. Additionally, the CCI database 408may provide a folder hierarchy storage system separate from the contentmanagement system 100. In this case, folders would be saved as anadditional data structure in the CCI database 408.

Each collaborative content item data element 650 is composed of a numberof elements. In some embodiments, the elements are as follows:

CollaborativeContentItemID: a unique identifier assigned by thecollaborative content management system 130 to access the collaborativecontent item.

AuthorID: the userID of the user who created the collaborative contentitem, and may include the username of the user. These values may beencrypted for privacy.

Creation timestamp: indicates the date and time that the collaborativecontent item was created.

Text: The text of the collaborative content item is represented asstring of ASCII characters.

Attribute pool: Formatting attributes (e.g., bold, underline, italics,font, font size, line spacing, paragraphs, and the like) that are usedin the collaborative content item. The attribute pool is a set ofattributeIDs used in the collaborative content item; a native set ofattributeIDs and associated formats are provided by the collaborativecontent management system 130. The following table is an example of aportion of an attribute pool:

Attribute ID Formatting 0 None 1 Bold 2 Italic 3 Underline 4Strikethrough 5 Superscript 6 Subscript 7 Single Space 8 Doublespace . .. . . .

Attribute list: Formatting attributes are applied to portions of acontent item, such as text, by the attribute list. The attribute listelement is a list of (span=attributeID) pairs, where the attributeIDindicates the attribute(s) from the attribute pool and the spanspecifies the number of characters to which the attribute(s) is to beapplied when the text is rendered, starting from the end of the previousspan, so that the entire length of the collaborative content item iscoded for attributes. For example, the text “Text with bold, italic, andbold italic formatting.” would be attribute coded as {10-0, 4-1, 2-0,6-2, 6-0, 11=1 2, 12=0}.

ThreadID_list: a list of all threads that are associated with acollaborative content item. ThreadIDs in the ThreadID_list may representthreads of content level comments or threads of file-level comments.

FLThreadID_list: a list of all file-level threads 528 that areassociated with a collaborative content item. Thus, the FLThread_listcontains a subset of the threads in Thread ID list.

Author_list: a sequential list of the users who have contributed to thecollaborative content item text, according to the sequence ofcontributed or edited text portions, using the same coding pattern asattribute list, i.e., (span=userID) pairs. For example, the author_list{100=199, 50=54, 200=199} indicates that in a text of 350 characters,there is a sequence of three text portions, the user with userID 199authored the first portion with 100 characters, followed by userID 54who authored the second portion with 50 characters, followed again byuserID 199 who authored the third portion with the remaining 200characters.

The span coding of the attributes and authors is beneficial because itallows for efficient management of insertions and deletions of content.For example, when text is inserted or deleted, only a limited number ofspans following the insertion or deletion need to be modified (thosewith spans falling within or overlapping the span of the inserted ordeleted text), and spans that are not impacted do not need to beupdated, since their relative positions are unchanged. In otherembodiments, the author list may be organized in a different fashion;for example, with the userID of each author followed by a list of textportions edited by that user.

Each thread data element 652 is composed of a number of elements. Insome embodiments thread data element 652 includes the followingelements:

ThreadID: unique identifier assigned by the collaborative contentmanagement system.

CollaborativeContentItemID: the CollaborativeContentItemID of the filethat contains the thread.

Span: a delineated portion of the content of the identifiedcollaborative content item to which the thread applies. The delineatedportion is defined based on the type of the content. For example, a spanin text can be defined by the position of the first character in thespan, and the length of the span (in number of characters); a span in animage can be defined by a bounding region, for example a set of (X,Y)coordinates, relative to the image origin that define a polygon withinthe region; a span in a spreadsheet can be defined by a range of cellsby column and row numbers. For example, the span (50, 25) indicates atext portion starting at character position 50 within the collaborativecontent item and running 25 characters in length. As the content in thecollaborative content item is edited, the collaborative contentmanagement system 130 updates the span element of each thread. Forexample, if a five-character portion of the text before the span (50,25) is deleted, then the content management system will modify the spanof the thread to (45, 25). It is also possible for users to delete textincluded in the span. If all of the text included in the span of athread is deleted, then the span will have a null value and is removedby the collaborative content management system 130 (unless isFilelevelis True as described below).

In some implementations, only content level comments are associated witha span, in this case a thread of file-level comments may have a nullvalue for a span accompanied by a True value for the is Filelevelelement. This is one mechanism for a thread of comments to persist inthe CCI database 408 until the thread of comments is deleted, no matterwhat other content in the collaborative content item is removed oredited. For example, the title of a collaborative content item can bemodified (e.g., edited or deleted). This change may not affect thefile-level comment, even though file-level comment can be displayed asbeing associated with the collaborative content item title. For example,if a collaborative content item title is deleted, a file-level commentcan remain attached to a field or other designated title location withinthe collaborative content item. As another example, a user can edit acollaborative content item title. A file-level comment can remainattached to a designated title location within the collaborative contentitem that contains the edited collaborative content item title.

CommentID_list: a list element of commentIDs of the comment dataelements (e.g., comment data elements 654) included in the threadcorresponding to thread data element 652.

AuthorID_list: a list of userIDs of the authors of comments in thethread.

Audience_list. The Audience_list element is a list indicating the usersto whom the thread and its comments are displayed when accessing thecollaborative content item, and to whom notifications of changes in thethread are sent. The audience for a thread can be determined differentlyfor file-level comments than for content level comments. In variousimplementations, the audience of a content level thread may comprise oneor more of the userIDs of the i) the author of the collaborative contentitem containing the thread; ii) the authors of comments included in thethread; iii) the authors of any text included in the span for thethread; iv) any user mentioned in the span the thread via a userprimitive (further described below); v) any user mentioned in a commentvia user primitive; or vi) any user who has opened the collaborativecontent item; vii) any user who has edited the collaborative contentitem; or viii) any user who has created an association with thecollaborative content item, such as by marking it as a favorite orfollowed collaborative content item. In some implementations, anaudience for the thread may not be defined specifically for the thread,but instead may be identified dynamically as needed based on, e.g., useridentifiers associated with the comments or with the collaborativecontent item. The inclusion of an audience for each thread allows forcontrol of which users are notified of, and have access to specificcomments as further described below.

isFilelevel: a value indicating whether the thread is a file-levelthread (associated with the collaborative content item as a whole asopposed to a particular span) or whether the thread is a content levelthread (associated with a particular span in the collaborative contentitem). Before deleting a content level thread for having a null span,the collaborative content management system 130 checks the isFilelevelvalue for the thread to determine whether it should be deleted. IfisFilelevel is True, the thread will not be deleted. The isFilelevelelement is also used to determine how a thread is displayed. IfisFilelevel is True the thread is displayed in the collaborative contentitem as a file-level thread with no associated span. If isFilelevel isFalse then the thread is displayed as a content level thread and theassociated span is highlighted in the collaborative content item.

Each comment data element 654 is composed of a number of elements. Insome embodiments, comment data element 654 includes the followingelements:

CommentID: a unique identifier assigned by the collaborative contentmanagement system 130.

AuthorID: the userID of the author of the comment.

Content: an element storing the content of the comment, which mayinclude text, pictures, or other media.

Attribute_list: a list storing the formatting attributes for the text ofthe comment, in the same manner as described above for collaborativecontent items.

ThreadID: the threadID of the thread to which the comment belongs.

State: an enumerated variable storing a value indicating the state ofthe comment as either active or resolved.

Notification_list: the Notification_list element is a list of userIDsindicating the users to whom a notification of the comment has beensent, as further explained below. This list is updated each time anotification message including the comment is sent to specific user.

Acknowledgement_list: the Acknowledgement_list element is a list ofuserIDs indicating the status of each user with respect to the comment.For example, the Acknowledgement_list may indicate whether each user inthe Audience_list of the thread has yet viewed the comment, has read thecomment, acknowledges an instruction in the comment, or intends torespond later to the comment, or any other set of enumerated actions orstatus types. In various implementations, this list can be updatedwhenever the collaborative content editor 404 displays the comment to auser that has not yet seen the new comment or when a user selects acontrol in relation to a comment indicating the user's acknowledgementof the comment or the user's intention to respond to the comment. Insome embodiments, the collaborative content editor 404 may display avisual indication of users that have viewed a particular commentproximate to the comment in the display. Additionally, the collaborativecontent management system 130 may provide UI elements for indicatingstatus beyond applying a “read receipt” when a user views a comment fora first time.

Reaction_list: reactions are elements that represent reactions of eachuser in the audience of the thread to the comment. The reaction listcomprises a list of reaction values paired with userIDs. In someembodiments, an interface for providing reactions to each comment isprovided and a user may select a reaction using a pull down feature oranother such UI feature. An enumerated set of reactions is nativelyprovided (e.g., “Approve,” “Disapprove”, “Happy”, “Angry”, “Puzzled”with associated numeric codes 1 . . . 5). Upon selection of a reactionfrom a reaction interface the numeric code corresponding to the selectedreaction is added to the reaction list. For example, reaction pair (345,5) would indicate that the user with userID 345 had an angry reaction tothe comment. In some embodiments, the collaborative content editor 404displays a visual indication of each reaction proximate to the commentin the display.

User information is also stored as database entities. Each user includesthe following elements:

DocumentID_List: a list of collaborative content item identifiersaccessible by the user of the user identifier.

RoomID_List: a list of room identifiers of comment rooms accessible bythe user of the user identifier. A user may have access to multiplecomment rooms for a single collaborative content item.

AnonymousUserID_list: a list of anonymous user identifiers associatedwith the user. An anonymous user identifier for the user may begenerated for each of the collaborative content items based on the useridentifier of the user and the document identifier of the collaborativecontent item. In some embodiments, anonymous user identifiers are notstored by the system, but instead are reconstructed based on the storeduser identifier and document identifier.

ThreadID_list: a list of threads in which the user has posted a comment,or is otherwise allowed to access.

Avatar: an identifier that references an avatar, such as an image,associated with the user. The avatar is used as a representation of theuser. The avatar may be presented when the user provides a comment orupdates a collaborative content item to attribute changes to the user.

AnonymousAvatars_list: a list of anonymous avatars associated withanonymous user identifiers of the user. Each anonymous user identifiermay be associated with a different anonymous avatar identifier. In someembodiments, anonymous avatars are not stored in association with users,but instead are referenced by the anonymous user identifier.

CCI database 408 may also include a set of indices. These indices arelogical in nature and may be implemented in various ways, depending onthe underlying database design. A user index contains a list of allusers by their userID, and for each userID there is a list ofcollaborativeContentItemIDs. Each collaborativeContentItemID identifiesa collaborative content item to which the user of the userID isassociated and has access to. For each collaborativeContentItemID, thereis a status indicator that indicates whether the collaborative contentitem is active or inactive for the user. A collaborative content item isactive for the user sharing the collaborative content item until theuser deletes the collaborative content item. In some embodiments, whenthe user deletes the collaborative content item, the collaborativecontent item persists in the collaborative content item database 408remains associated with the user but status indicator is set toinactive, allowing the user to reactivate their sharing status with thecollaborative content item in the future. The collaborative content itemremains active for and associated with any other shared users.Alternatively, the collaborative content item may be deleted from theitem database 408, so that none of the shared users have access to itanymore. The user index is used to identify collaborative content itemsassociated with (shared with) a given user and the status of thosecollaborative content items with respect to the user. In someembodiments, a userID index also indicates the privileges the user haswith respect to each document that the user is associated with. A valuestored with each collaborativeContentItemID in the index indicateswhether the user has editing privileges, viewing privileges, and/orsharing privileges.

Collaborative content item database 408 can include a collaborativecontent item index. The collaborative content item index indicates, foreach document, a list of userIDs of users having access to thecollaborative content item, and an indication of whether the user isactive or inactive. This index can be an inverse of the user index andmay be stored together with the user index. The collaborative contentitem index may also indicate the privileges of each user associated withthe collaborative content item using an inverse implementation of theabove described user index.

Text Transcription

Audio to text transcription is the process by which spoken language isconverted to a text transcript representative of the speech.Transcription may be performed manually by a human transcriber,automatically by a transcription software, or using a combination ofmanual transcription and automated transcription. Text transcripts ofcaptured speech may be desirable or beneficial for a number of reasons.For example, text transcripts are searchable, take less computer memory,and can be used as an alternate method of presenting the correspondingspeech (e.g., as closed captioning).

Text transcription software translates recorded audio data to text usingan algorithm to recognize words or sounds spoken in the audio data. Insome embodiments, the text transcription software records the audio andconverts the recorded audio into a useable file including thetranscribed text. In other embodiments, the text transcription softwarereceives a previously recorded audio file (for instance, a file recordedexternal to the transcription software). Words and sounds spoken in theaudio data can be identified based on a lexicon maintained by the texttranscription program. A lexicon comprises a vocabulary of words orphrases recognized by the text transcription algorithm, wherein eachvocabulary word or phrase is mapped within the lexicon to the soundsthat represent it. In some embodiments, a lexicon is organized based onthe frequency at which words appear in a spoken language. For example,words such as “and” and “the” may be associated with a higher frequencyin an English transcription lexicon than less frequently used words suchas “ecosystem”. The lexicon used to transcribe an audio file into textcan be a generic or default lexicon used for all audio files, or can bea customized lexicon generated, for instance, for a particular speakeror set of speakers (as described below in greater detail).

In some embodiments, the text transcription process uses a machinelearning algorithm to customize the transcription of an audio file basedon characteristics of voices included within the audio file. Forinstance, the text transcription software can be trained on soundscorresponding to known words, spoken by a variety of male and femalevoices, with a variety of accents, and a variety of levels of backgroundnoise. Machine learning may additionally be used to improve the accuracyof the lexicon associated with the text transcription process, forinstance based on an identity of a speaker within an audio file. Forexample, a lexicon associated with a chef who frequently discussesingredients may associate a higher frequency with words such as “thyme”and “flour” than a standardized lexicon. In addition, identifiedspeakers may be associated with groups. A lexicon can be selected andapplied to a user's speech based on the groups with which the user orone or more speakers are associated. For example, an identified user maybe associated with a legal department group, and a lexicon associatedwith the legal department group can be applied to speech associated withthe user.

Text transcription software may additionally be trained to recognizemultiple speakers. In a scenario where speech of multiple speakers iscaptured within an audio file, differences in voice pitch, accent, andother speaking inflections can be used to identify particular speakers.The generated text transcript is then formatted based on the identifiedspeakers, for instance by using identifiers such as speaker names,speaker numbers, color coding, or other methods of representation inassociated with each portion of the text transcript.

Audio Capture, Search, and Playback

When meeting with one or more people, it is often difficult for meetingattendants to manually record notes effectively. Recording audio dataduring the meeting allows attendants of the meeting to focus on andparticipate in the immediate context of the meeting, and additionallyallows others to later review the meeting without relying on potentiallyincomplete or inconsistent notes. However, a downside of audio data isthe inability to query audio data using particular words or phrases,thus hindering the accessibility of audio data to those searching forportions of meeting audio using search terms. Providing an interfacethat associates a text transcription of audio to the audio data allowsusers to quickly search and access portions of an audio file, thusimproving user efficiency both during and after a meeting.

FIG. 7 is an example illustrating a process for performing a keywordsearch of audio data, according to some example embodiments.

As shown in FIG. 7, speakers 705A, 705B, and 705C participate in ameeting including a spoken discourse. In some embodiments, the meetingmay occur entirely or partly via a remote connection (e.g., a videocall). Additionally, fewer or additional speakers may be part of themeeting. The speech of the one or more speakers 705 is recorded as audiodata. The collaborative content management system 130 identifiesspeakers based on the recorded audio data. In one example, speakers areidentified by number (e.g., Speaker 1, Speaker 2, Speaker 3) and arelater manually associated with names or other identifiers. In anotherexample, the collaborative content management system 130 retains pastaudio profiles associated with users and automatically identifiesspeakers based on the recorded audio and the past audio profiles. Inanother example, speakers are identified based on names being spokenduring the meeting.

In some embodiments, a collaborative content management system 130 (notincluded within FIG. 7) is accessed via a mobile phone (such as mobilephone 708 of FIG. 7), a laptop computer, a microphone system, or anotherdevice capable of recording audio. The collaborative content managementsystem 130 records the audio data associated with the meeting, forinstance in response to a request from a user to record the meeting. Forexample, a collaboration document within the collaborative contentmanagement system 130 can include an audio capture graphical interfaceelement that, when interacted with, causes audio data to be recorded bythe mobile device 708. In other embodiments, external software or anexternal device is used to record audio data from the meeting betweenthe one or more speakers 705, and the recorded audio data issubsequently uploaded to the collaborative content management system130. The audio data is stored as an audio file 710 by the collaborativecontent management system 130 in association with a collaborationdocument. The document may contain additional content items, such asspreadsheets, figures, text, and so forth.

An audio to text transcription process, as described above, is used togenerate a text transcript 720 representative of the captured audiodata. Words and phrases in the text transcript 720 are associated withtimestamps in the audio file 710 that correspond to the portion of theaudio data representative of the words and phrases. In some embodiments,the collaborative content management system 130 stores the texttranscript 720 within an existing collaboration document associated withthe audio file 710. The text transcript 720 can be accessed and modifiedby users with access to the document. Users with access to the documentcan additionally submit a search query 715 via an interface in thecollaboration document. Upon receiving the search query 715, thecollaborative content management system 130 can perform a full documentsearch (i.e., a search of the text transcript, of text includedelsewhere within the collaboration document, and the like). Thecollaborative content management system 130 can return search results,some of which include portions of the text transcript that correspondingto portions of the audio data. In other embodiments, the collaborativecontent management system 130 can provide results in response toreceiving the search query 715 associated only with the text transcriptof the transcribed audio data. In the example shown in FIG. 7, thesearch query 715 is a word (“Neapolitan”). In other examples, searchqueries 715 may be shorter or longer text segments, such as partialwords, phrases, or sentences, or may identify a speaker name.

In response to receiving the search query 715, the collaborative contentmanagement system 130 identifies portions of the text transcript thatcorrespond to the query. In some embodiments, the collaborative contentmanagement system 130 identifies corresponding portions of the texttranscript based on matching the text of the search query or variants ofthe text of the search query to portions of the text transcript. In anexample where the search query identifies a speaker's name, thecollaborative content management system 130 identifies portions of thetext transcript that correspond to speech by the identified speaker orto mentions of the speaker's name by other speakers. The collaborativecontent management system 130 causes the display of a list or set ofsearch results 725 within a search results interface of thecollaborative content management system 130. In the example of FIG. 7,two search results 725 are displayed: “RYAN: What flavor do you eatfirst in Neapolitan ice cream?” and “TOREY: I don't know, I don't eatNeapolitan.” In some embodiments, each search result 725 is formatted toinclude a link to a location of the search result within the texttranscript included within the document. In other embodiments, portionsof the search results 725 including text of the search query 715 may beformatted (e.g., by bolding, highlighting, or underlining the result) toemphasize the search query text within each search result. For example,in the example of FIG. 7, the search term “Neapolitan” is bolded withineach search result.

Search results that correspond to the text transcript can be associatedwith an audio playback graphical interface element 730. In someembodiments, an audio playback element 730 is displayed next to or inconjunction with an associated search result, and may be interacted withby a user viewing the search results 725. The audio playback element 730is associated with a portion of the captured audio data 710representative of the associated search result text. When selected, theaudio playback element 730 accesses and causes playback of theassociated portion of the captured audio data. For example, as shown inFIG. 7, an audio playback element 730A corresponds to the first searchresult (“RYAN: What flavor do you eat first in Neapolitan ice cream?”)and an audio playback element 730B corresponds to the second searchresult (“TOREY: I don't know, I don't eat Neapolitan.”) generated by thesearch query 715 (“Neapolitan”). The first audio playback element 730Acorresponds to a portion of the audio data 735A, and the second audioplayback element 730B corresponds to a portion of the audio data 735B.In a case where the second audio playback element 730B is selected, thecollaborative content management system 130 accesses the correspondingportion of the audio data 735B and causes playback of the audio data tothe querying user. For instance, the audio data 735B includes speechspoken by Torey saying “I don't know, I don't eat Neapolitan.”

FIG. 8 is an example flow chart illustrating a method for audio capture,search, and playback. The collaborative content management system 130receives 805 captured audio data, which may be recorded by or uploadedto the collaborative content management system 130. The captured audiodata is transcribed 810 into text, producing a document including a texttranscription of the audio file. The text document is indexed such thatwords or phrases in the text transcription correspond to portions of theaudio representative of the words or phrases. The collaborative contentmanagement system 130 receives 815 a search query from a user of thecollaborative content management system 130 with access to the document.Based on the search query, the collaborative content management system130 identifies 820 text portions corresponding to the search query andreceives 825 a user selection of an identified text portion. Based onthe selection of the text portion, the collaborative content managementsystem 130 identifies 830 portions of audio data that correspond to theselected text portion. The selection text portion and the correspondingportions of audio data are presented to the user, and, when selected,cause playback of the portion of audio data 835 associated with theselection text portion.

Automated Summary Generation of Captured Meeting Audio

Meeting audio for meetings between two or more people frequently containextraneous information, making it difficult to quickly access key pointsand topics of the meeting. Summaries or outlines make importantinformation (such as deadlines, assignments, and decisions) moreaccessible to users. However, manually generated summaries or outlinesmay be time consuming to create, unreliable, or inconsistent in quality.Providing an interface to automatically generate a meeting summary ormodify a document by, at least in part, identifying hot words thatcorrespond to actions streamlines the process of creating a meetingsummary and allows users to efficiently perform actions within acollaborative document by voice command alone.

FIG. 9 is an example illustrating the generation and incorporation of ameeting summary into a document.

A collaborative document 905 includes audio data 910 representing speechof one or more speakers. The audio data 910 may be recorded by thecollaborative content management system 130, uploaded from an externalsource, and/or stored in conjunction with the collaborative document 905(for instance, within metadata of the collaborative document, within asame folder as the collaborative document, and the like). In someembodiments, the audio data 910 is embedded into the collaborativedocument such that the collaborative content management system 130 mustaccess the document 905 in order to access the audio data 910. Thecollaborative document 905 may additionally contain other objects, suchas images, charts, spreadsheets, or text 915 as shown. The additionalobjects may or may not relate to the subject matter or contents of theaudio data (e.g., by topic, by date created or added to the document).

The collaborative content management system 130 uses an audio to texttranscription process, as described above, to generate a text transcript920 representative of the audio data. In some embodiments, thecollaborative content management system 130 embeds the text transcript920 within the collaborative document 905 associated with the audio file910. As shown in FIG. 9, the embedded transcript 935 may be labeled forclarity and formatted to fit within an allotted space at a location inthe collaborative document 905. In one example, the collaborativecontent management system 130 labels the text transcript 920 (e.g. as“transcript,” with an associated date or timestamp). In another example,the text transcript 920 may include information identifying the one ormore speakers associated with each portion of the audio data 910. Inanother example, the transcript is embedded within the collaborativedocument 905 (for instance, at the bottom of the collaborativedocument), such that only a portion of the transcript 920 and an expandinterface element are visible upon accessing the collaborative document.When a viewing user with access to the document 905 interacts with theinterface element, the element expands to display the full embeddedtranscript 920 within the document.

Based on the generated text transcript 920, the collaborative contentmanagement system 130 identifies a portion of text associated with a“create outline” action to generate a text outline 925. The text outline925 identifies main points and topics of the text transcript 920. Insome embodiments, the collaborative content management system 130identifies main points and topics of the text transcript 920 forinclusion in the outline 925 by identifying common or pre-determinedkeywords or hot words within the text transcript, times and dates withinthe text transcript, deadlines within the text transcript, conclusionsand resolutions reached within the text transcript, assignments made,and the like. For example, the text transcript 920 shown in FIG. 9including “JOEY: Create outline. Do you want to meet at 6 PM for dinnertonight? AMY: Sure. We can do brunch tomorrow before driving, too...” isused to generate a text outline including the objects “6 PM dinner” and“Brunch tomorrow.” In another example, a text transcript can include thetext “Chris: I am going to have Clark take over Rosemary's account”, andthe assignment outline object “Clark taking over Rosemary's account” isincluded in the outline. In yet another example, the text transcript caninclude the text:

Anne: Does anyone have any vacation ideas?

Rajiv: How about Mexico? It is nice this time of year.

Antonia: I've been wanting to go to Spain for a long time.

Toney: You can't get good Irish whiskey in either of those places.

In this example, the itinerary outline object “Vacation ideas: Mexico,Spain, Ireland” can be generated based on the keywords “vacation ideas”,“Mexico”, and “Spain”, and the inferred keyword “Ireland” (inferredbased on the phrase “Irish whiskey” in the context of vacationlocations). It should be noted that outline objects can further includean identity of a meeting participant or speaker associated with theoutline object (for instance, by including the text of participant'sname in an outline object, or by tagging the participant in the outlineobject).

The collaborative content management system 130 modifies thecollaborative document 905 to incorporate the generated text outline 925at a first location within the document 905. For example, the textoutline is embedded at the top of the collaborative document abovecontents of the collaborative document, as shown in FIG. 9. In someembodiments, objects in the text outline are additionally associatedwith audio playback elements displayed in conjunction with or next tothe objects. When selected, the audio playback element accesses andcauses playback of a portion of the captured audio data 910 associatedwith the outline objects. In other embodiments, the text outline 925 mayassociate outline objects with a link that, when selected, navigates auser to a location in the embedded text transcript 935 where textcorresponding to the outline object appears. In some embodiments, asshown in FIG. 9 and described above, the collaborative contentmanagement system 130 recognizes inferred keywords or variations onpre-determined keywords or hot words when identifying actions to take orgenerating outlines. For example, the collaborative content managementsystem 130 may identify singular and plural forms of words (e.g.,“invite a person” and “invite people” when triggering an action to addusers to a document) and related words (e.g., “Irish” to “Ireland” as inthe example above) as functionally interchangeable.

The generated text outline 925 can be modifiable by users with access tothe collaborative document 905 in which the outline is embedded. Usersmay add, edit, or delete objects within the text outline 925.Additionally, users may add comments, format objects (e.g., byhighlighting, bolding, underlining, or italicizing words or phrases),tag other users within the outline, or otherwise modify the generatedoutline 925. Modifications are incorporated by the collaborative contentmanagement system into the generated outline 925 and are displayed toother users with access to the document 905. In some embodiments, thecollaborative content management system 130 tracks and formatsmodifications made by users. For example, the collaborative contentmanagement system 130 identifies a user responsible for an edit whenincorporating the edit into the outline 925. It should be noted that inembodiments where the collaborative document 905 and the captured audiodata are associated with a meeting, participants in the meeting may takenotes or edit contents of the document during the meeting (such ascontents 915), and that these changes to the document can be preservedand displayed, for instance below the generated outline 925 and abovethe text transcript 935.

In other embodiments, the collaborative content management system 130identifies portions of text associated with additional actions ordocument modification. In one example, the identified portions of textare keywords or “hot words.” Each identified hot word is associated withan action taken by the collaborative content management system 130 tomodify the document. In some embodiments, hot words are predetermined,such that speaking a hot word triggers the performance of an associatedaction. For example, hot words may be predetermined by the collaborativecontent management system 130 based on words frequently used duringmeetings to identify important points (e.g., “deadline,” “task,”“assign”) or words used to designate an action commonly performed by thecollaborative content management system 130 (e.g., “share,” “invite,”“tag”). In other embodiments, hot words may be defined by users andmanually associated with actions to be taken by the collaborativecontent management system 130 upon identifying the hot word in the audiodata. In some embodiments, a set of hot words may trigger theperformance of an action for any speaker in the audio data, while inother embodiments, certain hot words only trigger the performance of anaction if a particular speaker speaks them (for instance, a manager, ameeting leader, a speaker with particular access privileges, and thelike). The collaborative content management system 130 may identifymanually defined hot words and associated actions (and in someembodiments, an identity of the speaker) on a per-document basis, orbased on the identity, position, or access privileges of the documentowner, meeting leader, or speaker within the audio data. Based on theactions associated with the identified hot words, the collaborativecontent management system modifies the collaborative document. Themodified document is then displayed and can be accessed, viewed, andmodified by users with access and modification permissions to thedocument. In some embodiments, as described above in conjunction withFIG. 9, the collaborative content management system 130 transcribes thecaptured audio data into text representative of the speech. When hotwords are identified in the audio data, the collaborative contentmanagement system 130 modifies the collaborative document to generate atext outline of the captured audio data. In other embodiments, a hotword is associated with an action to generate a summary for at least aportion of the audio data. When a hot word is identified, thecollaborative content management system 130 generates at least a portionof a text outline summarizing the audio data corresponding to the hotword.

Some hot words are associated with actions that modify a collaborativedocument to include text, for instance identifying an action item, adecision made during the meeting, a task or project assignment, or otherinformation. For example, the collaborative content management system130 identifies a hot word in the audio data associated with an actionitem (such as the words “action item” or “to-do”) and modifies the textof the collaborative document to include text identifying the actionitem. The modification may include additional information about theaction item, such as one or more people associated with the action item,a due date, and a status. In cases where one or more people areassociated with the action item, the collaborative content managementsystem 130 may tag the users within the document. In another example,the collaborative content management system 130 identifies a hot word inthe audio data associated with a task assignment (such as the words“assign to” or “assignment”) and modifies the text of the collaborativedocument to include text identifying the assignment. As previouslymentioned, the modification may include additional information such as adue date of the task or a user to which the task is assigned. In anotherexample, the collaborative content management system 130 identifies ahot word in the audio data associated with a decision made during ameeting (such as the words “final decision” or simply “decision” or“decides”) and modifies the text of the collaborative document toinclude text representative of the decision (for instance, in a bulletpoint within a meeting outline).

Some hot words are associated with actions that include a tag or a linkwithin a collaborative document. For example, the collaborative contentmanagement system 130 identifies a hot word within the audio dataassociated with a tag action (such as “tag” or “include”, followed by anidentification of a user) and modifies the collaborative document bytagging an identified user within the document (for instance, a meetingparticipant, or someone that did not participate in the meeting but thata meeting participant wants to be able to access the collaborativedocument). In another example, the collaborative content managementsystem 130 identifies a hot word within the audio data associated with alink action (such as “include link” or “hyperlink”, followed by a linkaddress) and modifies the collaborative document to include a link that(when interacted with) causes a direction to the link address within thecollaborative document. In some embodiments, the link may lead toanother document, object, network address, website, URL, or any othersuitable destination.

Some hot words are associated with actions that alter the permissionsassociated with the collaborative document. For example, thecollaborative content management system 130 identifies a hot word withinthe audio data associated with a share action (such as the words “share”or “grant permission”) and modifies the permissions of the collaborativedocument based on the permissions and users identified in the speechassociated with the hot word. For instance, a user might say “grantpermission to Calvin to edit the document”, and the user Calvin can begranted editing permissions for the document. In another example, a hotword within the audio data is associated with an invite action (such asthe words “invite” or “add” followed by a user identity), and thecollaborative content management system 130 can send an invite to thecollaborative document to the identified user (and can also modify theaccess permissions of the collaborative document to allow the user toview or modify the document in response to the hot word).

In some embodiments, hot words can be used to modify a document after ameeting has completed. For instance, the collaborative contentmanagement system 130 can access audio data captured during a meetingafter the conclusion of the meeting, can access a collaborative documentassociated with the meeting, and can modify the collaborative documentbased on hot words included within the audio data. In other embodiments,the collaborative content management system 130 can capture audio dataand modify a collaborative document based on hot words within the audiodata in real-time. For example, the collaborative content managementsystem 130 can access a collaborative document associated with ameeting, and, during the course of the meeting, can add text to thedocument, tag users within the document, include text representative oftask assignments within the document, and change access permissions forthe document in response to detecting hot words spoken by one or morespeakers during the meeting.

FIG. 10 is an example flow chart illustrating a method for modifying adocument based on captured audio data. The collaborative contentmanagement system 130 accesses 1005 captured audio data associated witha document. The audio data may be recorded by the collaborative contentmanagement system 130 or uploaded from an external source by a user ofthe collaborative content management system 130. Using an audio to texttranscription program as described above, the collaborative contentmanagement system 130 transcribes 1010 the audio data into text. Basedon the text transcription, the collaborative content management system130 identifies 1015 text in the text transcription associated withcandidate document modifications and modifies 1020 the document based onthe candidate document modifications associated with the identifiedtext. A “candidate document modification”, as used herein, is associatedwith a portion of text (such as a keyword, hot word, or phrase) andrefers to a modification that, when the associated portion of text isidentified within a text transcription, is performed on a document. Insome embodiments, a text portion within the text transcription isassociated with a modification rule that is associated with a documentmodification to be made when the modification rule is satisfied. Forinstance, a modification rule can indicate that when the text “to do” isdetected within a text transcription, a corresponding document is to bemodified to include the text “to do” along with an associated portion ofthe text transcription that follows the term “to do”.

Meeting Transcription Using Custom Lexicons Based on Document History

As noted above, audio to text transcription relies on a lexicon torecognize words and sounds spoken within audio data. A lexicon ismaintained by the text transcription program, and comprises a vocabularyof words or phrases mapped to representative sounds. In someembodiments, standard lexicons are organized based on the frequency atwhich words appear in a spoken language. As used herein, “standardlexicon” refers to a default lexicon used by a transcription system.However, because words may be used at differing frequencies depending onthe context or speaker, it may be beneficial for the text transcriptionprogram to generate customized lexicons based on historic word usage.Custom lexicons enable a text transcription system to more accuratelyidentify words or phrases that are frequently or uniquely used by aspeaker or in a particular context that might otherwise be uncommon in astandard lexicon. As used herein, “custom lexicon” refers to a lexiconused by a transcription system for a corresponding subset of one or moreusers. While custom lexicons may be developed based on previouslytranscribed audio data, it is more comprehensive to develop a customlexicon based on user documents in addition to audio data. By usingdocuments saved to a content system such as spreadsheets, textdocuments, and others, the text transcription program has a great poolof data to mine in order to generate a customized lexicon for the user.

FIG. 11 is an example illustrating the generation and application of acustom lexicon to create a meeting transcript.

As shown in FIG. 11, a user 1105 of the collaborative content managementsystem 130 is associated with a user document store 1110. In someembodiments, the user document store 1110 includes collaborativedocuments that a user 1105 has permission to access or modify, forinstance within the collaborative content management system 130, on oneor more user devices, or at any other suitable location. For example,the user document store 1110 associated with a user 1105 may includedocuments created by the user, documents shared with the user by otherusers of the collaborative content management system 130, documents inwhich the user is tagged, documents in which the user has viewing ormodifying permissions, documents the user has uploaded from a userdevice, documents the user has shared from another online account, andthe like. The user documents 1115 can be spreadsheets, text documents,video or audio files, slideshows, images, or any other suitabledocument.

The collaborative content management system 130 accesses one or moredocuments 1115 stored in the user document store 1110 to generate acustom lexicon 1120 for the user 1105. The collaborative contentmanagement system 130 identifies words and phrases used frequently bythe user 1105 based on text included within the accessed documents 1115.For example, the text can include raw text, image captions, texttranscriptions of audio data, spreadsheet data, and other formatted orunformatted text contained within the user documents 1115. In someembodiments, the collaborative content management system 130 identifieswords, n-grams, and phrases included within the set of user documents1110 that aren't otherwise included within a default lexicon, andincludes the words, n-grams, and phrases (mapped to correspondingsounds) within the default lexicon to create the custom lexicon. In someembodiments, the collaborative content management system 130 adjusts anordering of words within a default lexicon based on identified words,n-grams, and phrases from the set of user documents to prioritize words,n-grams, and phrases used more frequently by the user than expectedand/or to de-prioritize words, n-grams, and phrases used less frequentlyby the user than expected. In some embodiments, the collaborativecontent management system 130 generates a custom lexicon based on words,n-grams, and phrases included within the accessed set of user documents.In such embodiments, the collaborative content management system 130 canfirst attempt to generate a text transcript for a user's speech usingthe custom lexicon associated with the user, and can secondarily use adefault lexicon for words, n-grams, and phrases not included in thecustom lexicon.

When the collaborative content management system 120 receives audio datato be transcribed into text, a custom lexicon 1120 can be selected basedon an identity of one or more speakers within the audio data or based ona context of the audio data (such as an HR group meeting, or a recordedspeech by a manager). The custom lexicon 1120 can then be used to moreaccurately recognize the words and phrases included within the receivedaudio data, and in turn to generate a more accurate text transcript. Asshown in FIG. 11, when the audio data corresponds to one speaker, thedocuments 1115 of the user document store 1110 associated with the user1105 are used to generate a custom lexicon 1120 that is then used togenerate a text transcript of the audio data. For instance, audio dataassociated with the user 1105 and representative of the phrase “Ilearned how to speak Klingon” is provided to the collaborative contentmanagement system 130 for transcription. The user 1105 is additionallyassociated with one or more user documents 1115 in which the words“Vulcans,” “Klingons,” and “Andorians” are used. The collaborativecontent management system 130 modifies a generic lexicon to includethese terms from the one or more user documents 1115 to generate acustom lexicon 1120. Using the custom lexicon 1120, the collaborativecontent management system 130 generates a text transcript 1125 (“FIONA:I learned how to speak Klingon”). The collaborative content managementsystem 130 can then cause display of the text transcript 1125 to theuser 1105 in the collaborative document associated with the audio data.It should be noted that in some embodiments, after a speaker isidentified, a pre-generated custom lexicon can be accessed and used togenerate a text transcript (as opposed to generating a custom texttranscript each time a text transcription operation is performed).

In other embodiments, the audio data received by the collaborativecontent management system 130 represents multiple speakers, one or moreof which are associated with a user document store 1110. When multiplespeakers are represented in the audio data (for example, as in audiodata of a meeting), the collaborative content management system 130 usesdocuments associated with one or more of the speakers to generate acustom lexicon. In some embodiments, the collaborative contentmanagement system 130 accesses custom lexicons associated with each ofthe one or more speakers to produce a custom lexicon inclusive ofvocabulary in each of the speakers' custom lexicons. In otherembodiments, a custom lexicon is generated for the one or more speakersby selecting one custom lexicon representative of the meeting from amongthe custom lexicons associated with each of the one or more speakers.For example, the collaborative content management system 130 may selecta custom lexicon associated with one speaker based on the subject matterof the audio data, one or more characteristics of the one or morespeakers, a size of vocabulary associated with each custom lexicon, orbased on any other suitable factor. In other embodiments, a customlexicon is generated for the one or more speakers based on a selectedset of documents. The set of documents may be selected from the userdocument stores of the one or more speakers. For example, thecollaborative content management system 130 may generate a customlexicon based on documents accessible to each of the one or morespeakers, documents selected by a speaker of the one or more speakers,documents associated with a subject matter of the audio data, documentsassociated with a meeting leader, or based on any other suitablecriteria. In another example, the collaborative content managementsystem 130 may generate a custom lexicon based on a union of documentsstored within an account associated with each speaker of the one or morespeakers.

In some embodiments in which the audio data is captured during a meetingwith one or more speakers, the subject matter and/or characteristics ofthe meeting may be used to select a set of documents from which togenerate a custom lexicon. For example, documents may be selected fromthe user document stores of one or more speakers based on the documentscorresponding to a subject of the meeting.

In some embodiments, a second custom lexicon may be generated inresponse to a first custom lexicon not including a word or phrasecorresponding to a portion of audio data.

The second custom lexicon may be generated based on a second set ofdocuments, selected as described above. In some embodiments, the secondset of documents is associated with a second subset of the speakersrepresented in the audio data different from the subset of speakers usedto generate the first custom lexicon. The second custom lexicon is thenused by the collaborative content management system 130 to transcribethe audio data.

It should be noted that in some embodiments, a custom lexicon isgenerated for each speaker within audio data, and the collaborativecontent management system 130 selects among the custom lexicons for usein transcribing the audio data based on an identity of the speaker. Forinstance, a first custom lexicon associated with a first speaker can beused to transcribe audio of the first speaker saying “Did you go seeBlink 182 this weekend” and a second custom lexicon associated with asecond speaker can be used to transcribe audio of the second speakerresponding “No, I went to the Reel Big Fish concert instead”.

FIG. 12 is an example flow chart illustrating a method for generating atext transcript using a custom lexicon based on document history. Thecollaborative content management system 130 receives 1205 audio datacorresponding to a document. The audio data may be recorded by thecollaborative content management system 130 (for instance, during ameeting) or uploaded from an external source. The document mayadditionally include other content objects such as spreadsheets, images,plain text, charts, and others. The collaborative content managementsystem 130 accesses 1210 a custom lexicon generated based on documentsassociated with one or more speakers in the audio data. Using the customlexicon, the collaborative content management system 130 transcribes1215 the audio data into text and modifies 1220 the document associatedwith the audio data to include the text transcript.

Additional Considerations

Reference in the specification to “one embodiment” or to “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiments is included in at least oneembodiment. The appearances of the phrase “in some embodiments” invarious places in the specification are not necessarily all referring tothe same embodiment.

In this description, the term “module” refers to a physical computerstructure of computational logic for providing the specifiedfunctionality. A module can be implemented in hardware, firmware, and/orsoftware. In regards to software implementation of modules, it isunderstood by those of skill in the art that a module comprises a blockof code that contains the data structure, methods, classes, header andother code objects appropriate to execute the described functionality.Depending on the specific implementation language, a module may be apackage, a class, or a component. It will be understood that anycomputer programming language may support equivalent structures using adifferent terminology than “module.”

It will be understood that the named modules described herein representone embodiment of such modules, and other embodiments may include othermodules. In addition, other embodiments may lack modules describedherein and/or distribute the described functionality among the modulesin a different manner. Additionally, the functionalities attributed tomore than one module can be incorporated into a single module. Where themodules described herein are implemented as software, the module can beimplemented as a standalone program, but can also be implemented throughother means, for example as part of a larger program, as a plurality ofseparate programs, or as one or more statically or dynamically linkedlibraries. In any of these software implementations, the modules arestored on the computer readable persistent storage devices of a system,loaded into memory, and executed by the one or more processors of thesystem's computers.

The operations herein may also be performed by an apparatus. Thisapparatus may be specially constructed for the required purposes, or itmay comprise a general-purpose computer selectively activated orreconfigured by a computer program stored in the computer. Such acomputer program may be stored in a computer readable storage medium,such as, but is not limited to, any type of disk including opticaldisks, CD-ROMs, read-only memories (ROMs), random access memories(RAMs), magnetic or optical cards, or any type of media suitable forstoring electronic instructions, and each coupled to a computer systembus. Furthermore, the computers referred to in the specification mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

The algorithms presented herein are not inherently related to anyparticular computer or other apparatus. Various general-purpose systemsmay also be used with programs in accordance with the teachings herein,or it may prove convenient to construct more specialized apparatus toperform the required method steps. The required structure for a varietyof these systems will appear from the description above. In addition,the present invention is not described with reference to any particularprogramming language. It will be appreciated that a variety ofprogramming languages may be used to implement the teachings of thepresent invention as described herein, and any references above tospecific languages are provided for disclosure of enablement and bestmode of the present invention.

While the invention has been particularly shown and described withreference to a preferred embodiment and several alternate embodiments,it will be understood by persons skilled in the relevant art thatvarious changes in form and details can be made therein withoutdeparting from the spirit and scope of the invention.

As used herein, the word “or” refers to any possible permutation of aset of items. Moreover, claim language reciting ‘at least one of’ anelement or another element refers to any possible permutation of the setof elements.

Although this description includes a variety of examples and otherinformation to explain aspects within the scope of the appended claims,no limitation of the claims should be implied based on particularfeatures or arrangements these examples. This disclosure includesspecific embodiments and implementations for illustration, but variousmodifications can be made without deviating from the scope of theembodiments and implementations. For example, functionality can bedistributed differently or performed in components other than thoseidentified herein. This disclosure includes the described features asnon-exclusive examples of systems components, physical and logicalstructures, and methods within its scope.

Finally, it should be noted that the language used in the specificationhas been principally selected for readability and instructionalpurposes, and may not have been selected to delineate or circumscribethe inventive subject matter. Accordingly, the disclosure of the presentinvention is intended to be illustrative, but not limiting, of the scopeof the invention, which is set forth in the following claims.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a content creation system, audio data including speech ofone or more speakers, the audio data corresponding to a collaborationdocument; accessing, by the content creation system for a subset of theone or more speakers, a custom lexicon generated based on a set ofdocuments associated with the subset of speakers and stored by thecontent creation system; transcribing, by the content creation system,the audio data into text representative of the speech using the customlexicon; and modifying, by the content creation system, thecollaboration document to include the text representative of the speech.2. The computer-implemented method of claim 1, wherein the subset of theone or more speakers comprises one speaker.
 3. The computer-implementedmethod of claim 1, wherein generating the custom lexicon comprises:identifying, by the content creation system, a set of words or n-gramsincluded within the set of documents; and modifying, by the contentcreation system, a default lexicon to include the identified set ofwords or n-grams to generate the custom lexicon.
 4. Thecomputer-implemented method of claim 1, wherein accessing the customlexicon for the subset of speakers comprises selecting among a pluralityof lexicons associated with each speaker of the subset of speakers basedon a subject matter of the audio data.
 5. The computer-implementedmethod of claim 1, wherein accessing the custom lexicon for the subsetof speakers comprises selecting among a plurality of lexicons associatedwith each speaker of the subset of speakers based on one or morecharacteristics of the one or more speakers.
 6. The computer-implementedmethod of claim 1, wherein the set of documents is accessible to each ofthe subset of speakers.
 7. The computer-implemented method of claim 1,wherein each document of the set of documents is stored within anaccount of one or more of the subset of speakers.
 8. Thecomputer-implemented method of claim 1, wherein the set of documentscomprises a union of documents stored within an account associated witheach speaker of the subset of speakers.
 9. The computer-implementedmethod of claim 1, wherein at least one document of the set of documentscomprises the collaboration document.
 10. The computer-implementedmethod of claim 1, wherein the set of documents is associated with asubject matter of the audio data.
 11. The computer-implemented method ofclaim 1, wherein the set of documents is selected by a speaker of theone or more speakers.
 12. The computer-implemented method of claim 1,wherein the audio data is captured during a meeting.
 13. Thecomputer-implemented method of claim 12, wherein the set of documents isselected based on a characteristic of the meeting.
 14. Thecomputer-implemented method of claim 1, wherein a second custom lexiconis accessed in response to the custom lexicon not including textassociated with a spoken word.
 15. The computer-implemented method ofclaim 14, wherein the second custom lexicon is generated based on asecond set of documents.
 16. The computer-implemented method of claim15, wherein the second set of documents is associated with a secondsubset of speakers different from the first subset of speakers.
 17. Thecomputer-implemented method of claim 1, wherein accessing a customlexicon comprises accessing a plurality of lexicons including the customlexicon, wherein each lexicon of the plurality of lexicons correspondsto a particular speaker of the subset of speakers.
 18. A systemcomprising: a processor; and a non-transitory computer-readable storagemedium storing executable instructions that, when executed by theprocessor, cause the processor to perform steps comprising: receivingaudio data including speech of one or more speakers, the audio datacorresponding to a collaboration document; accessing, for a subset ofthe one or more speakers, a custom lexicon generated based on a set ofdocuments associated with the subset of speakers and stored by thecontent creation system; transcribing the audio data into textrepresentative of the speech using the custom lexicon; and modifying thecollaboration document to include the text representative of the speech.19. The system of claim 18, wherein the custom lexicon includes a set ofterms included within the set of documents and not included within adefault lexicon.
 20. A computer-implemented method comprising:receiving, by a content creation system, audio data including speech ofone or more speakers; accessing, by the content creation system for asubset of the one or more speakers, a custom lexicon generated based ona set of documents associated with the subset of speakers; andtranscribing, by the content creation system, the audio data into textrepresentative of the speech using the custom lexicon.